That would be awesome indeed. I love that about Premiere too. Lightroom Classic is a lot more configurable then the cloudy version of Lightroom but still not as much as Premiere and most other Adobe apps with palettes that tear off and can go to other screens and such. ... View more

Copying the catalog should work but it is likely to result in things being out of sync if you don't follow the exact same steps every time and copy everything - not just the lrcat file. It is MUCH easier to just store the catalog and all associated files on the external and open that directly on both computers - no copying so no chance to be out of phase.   There is no correct method. Adobe really didn't seem to have envisioned using multiple computers with the same catalog originally and the general solution for this has always been to put the catalog on a portable drive which is very reasonable thing to do with big SSD externals nowadays. They created the cloudy version of lightroom as a solution for that when the voices got very loud for a multiple computer but same catalog solution years ago.  ... View more

Can you show some screenshots of what is happening before and after applying the settings? Also what hardware are you running on? ... View more

Agree with all the other folks. The issue is that the catalog is not the same. Something in the copy process did not work correctly or you are opening the wrong catalog on one computer. The trick to make this (having the same catalog on both machines) work reliably is to put the catalog on the external drive and open it directly from there on both machines instead of copying it every time. This has the advantage of all the support files (the data file, previews, etc.) coming with in a consistent manner and ensures that the catalogs are always identical since it is the same file you are opening. ... View more

It really shouldn't show this error if the .Trashes folder is there and you have permission to write to that folder. I can delete images stored on external drives without any issue in Lightroom Classic and it does not show the error message. It just moves the images into the trash. The only time I have seen this is when an external drive was missing the folder. Mac OS should automatically create this hidden folder but sometimes doesn't usually if there is a permissions issue with the external drive. Permission issues arise for example if it was used in another machine with another username and you do not have "ignore ownership on this volume" checked when you do a get info on the drive. If your externals are ssd, Apple recommends using APFS for the formatting but Mac OS extended (Journaled) is fine for spinning magnetic disks. ... View more

I get the warning that because my external hard disk (where those photos reside) isn't allowed to use the "Bin", the photos have to be deleted immediately. This is a faulty assumption by LrC since I can easily "delete" (i.e. move to the Bin) any file on that external HD outside of LrC...   That's a known Mac OS problem/bug where it doesn't create a trash bin on external volumes. If the external volume doesn't have the hidden ".Trashes" folder (which is how it implements trash bins on volumes) in it's root directory, Mac OS will tell programs that want to delete a file that this is a volume that has no trash/recycle bin. The trick is to create this folder from the commandline and to make sure it has group staff assigned to it and this error message in Lightroom Classic will go away. I am pretty sure this only is a problem on non-native filesystems like exFAT or NTFS and that if you format the drive as APFS, Mac OS creates the folder by default but that is something to check I guess.         ... View more

I understand your frustration but the Adobe folks will probably tell you that this is as designed. I am not an Adobe engineer, just a fellow user and this is how I understand the preview database is implemented after being surprised myself I could not directly decrease the size of the database and researching the issue. Discarding doesn't delete the files instantaneously. It just marks them out of date and in the background the actual files are deleted over time and only if they were actually not needed. Standard previews are generated automatically for images in your database that don't have them if there is some request to see them which is triggered by just browsing through the folder in Classic. So while not automatic, just browsing through will kick off a regeneration of the preview. Think of discarding in its literal meaning as casting aside or putting in a trash bin. That doesn't delete the items immediately but marks them as not needed. What your discard action does is akin to sticking a "get rid of this" post-it on the thing you're discarding. They are not actually gone until somebody permanently deletes them. There basically is a clean up service that goes through the building (your preview database) and takes out the trash (the previews you marked discarded). It can take a while before it gets to the room you're cleaning up in and even then it might decide that "hey they actually did use this after they put on the post-it so I am not yet getting rid of this quite yet".   This is what Google's AI says when comparing discard vs delete which is consistent with the dictionary meanings of these words: "Discard" often means getting rid of something unwanted (like trash or a draft email) with a sense of personal choice, while "delete" usually implies permanent removal, especially in digital contexts (like deleting a file from a computer) . In software, "discard" might hide something from a view but keep it in the database, whereas "delete" permanently removes it, though the specifics depend on the application's design (e.g., some apps use discard for your own cards, delete for anyone's).    ... View more

The same thing is true for standard previews - sorry if I did not make that clear. The culling from the preview database for any size preview is not instantaneous. It is how they implemented it. I agree it would be preferable and logical if it were instantaneous but it clearly isn't. I have seen this on my catalogs where it will slowly decrease the preview database after you selected "discard standard and 1:1 previews". I think it won't actually discard standard previews in that case if you have recently touched or viewed the image - don't know what the time constant for that is. Also note that it will recreate standard previews in the background over time regardless if you discarded them so discarding standard previews usually has little effect. Only when you set the standard preview size to something smaller will you end up with a smaller preview database after discarding them since the recreated previews will be smaller size. ... View more

This is a long standing request that Adobe has not wanted to implement. See this thread from 2017 for example: https://community.adobe.com/t5/lightroom-classic-ideas/p-should-be-able-to-sync-full-raw-files-to-the-cloud-not-just-smart-previews/idc-p/15551079/page/5 ... View more

The (undocumented) trick to get full resolution raws in the cloud for images synced from Classic is the following. First sync your images from Classic resulting in smart previews in the cloud. Then open the cloud based Lightroom on your PC/Mac and see that the smart previews are there. A way to check is to turn on the info by clicking the small (i) button on the bottom right of the window. At the bottom of the info panel that pops up (sync status) you will see what kind of file is available in the cloud for the selected image. Now what you do is simply drag the full raw files from Finder/explorer onto Cloud-based Lightroom and it will/should upload the images to the cloud and associate the full raw with the already available smart preview. This is not 100% reliable but works correctly normally and should get you full resolution images to edit on your iPad.  ... View more

Hoe je dit doet is in een vorige versie veranderd. Er is geen menuoptie meer. In plaats van een boel platen selecteren en de menu optie gebruiken, wordt je nu verondersteld om de "sync" optie te gebruiken of makkelijker, de "auto-sync". Selecteer all beelden die je wilt ontruizen,  ga in Develop. Zorg ervoor dat auto-sync (rechts onder) is geselecteerd en klik de Detail->Denoise (sorry mijn Classic is in het Engels dus dit heet waarschijnlijk net iets anders). Nadat je dit hebt geklikt zal Classic automatisch al de geselecteerde beelden ontruizen. Hopelijk helpt dit.   Edit: Sorry niet goed gelezen. Johan had dit al geantwoord! ... View more

It takes a long time to actually remove the previews you discarded in my experience. I think it only marks the previews you discarded as removed and slowly cleans up in the background when it determines you actually wanted to get rid of them - i.e. you do not actually zoom in again to 1:1 to necessitate a 1:1 preview.  ... View more

The best way to do this is unfortunately not documented. What you do is sync your classic catalog to the cloud. This will upload smart previews of all your images. Now open Lightroom Cloudy on your desktop and you should see all images albeit in lower resolution. What you then do is drag the corresponding raw files (you can go folder by folder) and only the raw files (so no xmp metadata) onto Cloud-based Lightroom. This will upload the full raw files to the cloud and automatically associate the images with the already present smart previews without creating duplicates and Lightroom Classic will not download these files since it already has them. The method you did tends to create duplicates indeed since the image modification dates are off in Cloud-based Lightroom as it will take the import time. This is really the only way that works if you want to retain full capability in Classic. Do note however that classic needs a local copy of everything that is in the cloud. It cannot dynamically download from the cloud like Lightroom Cloudy can. So if you use Classic you always need the local copy of files.  ... View more

I've seen this problem for a long time on files from my Nikon Z7. It appears the vignette correction is not applied correctly before stitching. Which is no surprise since I know the built in lens profile based vignette correction is not quite correct even on single images so you get this kind of banding on overlapping areas. Indeed Photoshop has no problem with these since I think it calculates its own vignette correction based on overlap instead of using a lens profile. It is usually subtle for me and can be corrected but yeah it would definitely be amplified by filling in off missing areas which I rarely do. ... View more

John is right. This is not a normal observation and yes many of us here apply denoise AI to 100's of images at the same time. I never ever restart my machine except for system updates. AI denoise just keeps chugging along. This is likely a graphics card specific memory management bug in the GPU driver. Making sure your driver is up to date (you'll have to go to the manufacturer's website - windows update does not keep GPU drivers up to date very well) is known to fix similar issues. Make sure if you use a Nvidea card you install the studio driver - not the gaming one. If the driver update doesn't help, make sure you relay the info john asks for as that might help chasing down if there is indeed a deeper problem in Lightroom's code - which is entirely possible. ... View more

I don't see this happen so perhaps this is specific to the raw files you are using. Can you share a few that you are trying to merge? Just put a folder on dropbox or similar sharing service and post the link as the forum does not like to embed raw files. ... View more

It's already noted in this thread multiple times but to support a camera, Adobe needs to shoot reference charts with the camera in controlled lighting conditions and build profiles. Adobe only gets new cameras when the come out on the market. The camera makers unfortunately do not generally share cameras in advance with makers of third party raw converters. So when a new camera comes out, they have to go and buy one, shoot the reference charts, build profiles and only then can they provide support in the next release of the software. It's not about the file format! Anybody can read that. It is about the profiling of the camera. This is why you can often just edit the camera string in the raw file and fool Lightroom into supporting the images because it thinks it is dealing with files from an older camera. The color rendering is likely to be off but it will work. If only camera makers would either share prerelease cameras, we would have preliminary support earlier. Alternatively they could do their own profiling and use an open raw format like dng which includes embedded profiles which would give you support and consistent color from day one in any raw converter that supports dng files.  ... View more

You simply drag the folder inside Lightroom to another spot in the hierarchy on the left and it will move the folder and its content. It is a little difficult to move folders this way as the interface reacts (I.e. scrolls) way too fast if you have lots of folders inside classic. Also if you have any instability in the network connection, consider using finder/explorer to copy the folders you want to move and then doing a update folder location inside Lightroom Classic before deleting in the original location. While the dragging inside Lightroom method works fine, it is possible to lose images if the network is not stable. Copying and reconnecting in the new location avoids this (low probability but high impact) potential scenario. ... View more

No need to export. Simply do an archive on any album you want to move offline. You'll get a dialog that you can use to choose to store the images whereever you want.  ... View more

> 1) Can I really only have local files folders on the Mac Pictures folder on the main Disk - I don't see a setting to change this? and   Local images can be anywhere, including on external disks. Just point the local browser to any location where you put your images. This is easiest if you reveal the local file structure by clicking on the item that looks like a window right next to the three colored close/minimize/maximize lozenges in the upper left corner of the main window. Also when you have online images that you want to archive locally, which removes them from the cloud and stores them only locally, you get a dialog that allows you to specify any location you want.    >2) Because I have enabled saving of originals in cache it looks like they are going to fill my cache SSD so I am not going to gain any space.   You are better off not having a copy of all your cloud stored images available locally. Lightroom will automatically downoad what it needs and manage local storage for you if you use the default option of not doing that. Of course if you want to have a copy of all your images locally for security it is fine to do that but it is really not necessary. The best way to do it is to just keep your images in the cloud and when you don't need them there anymore, use the archive function as I descrobed above to move images to local storage. Again that can be anywhere on your system, including external disks, NAS servers, etc. ... View more

Lightroom Desktop can do panoramas and HDR the same way as Classic. Select all the images you want to merge in the grid view, right click and select Photo merge->Panorama merge. The same options are available in the "Photo" menu. These options are not avaiable on mobile platforms and in the web browser version (https://lightroom.adobe.com) if that is what you are using. ... View more

Yeah an unbelievably bad choice of names. I remember very heated discussions here and on other fora when they made the announcement. Very controversial and yeah people latched on the classic moniker as a very clear sign classic was on the way out. It is very possible that a decade ago they fully meant to retire classic in a few years but the pace of bringing Cloudy up to the same level has been fairly slow (how long did it take to get secondary monitor support!). I love cloudy for the simplicity of the interface and the mobile link and it is slowly getting better but not quite there yet and certainly not ready to be my main workflow and repository. The things I miss most and will likely never get in cloudy is nested keywords as well as a real local workflow. The local browser is very useful but very limited for organization without copying images to the cloud (no albums/collections/very limited searching, etc.). I also deal with a 1000 images on any day regularly and cloudy just doesn't deal with that very well. That said, there are many things in Classic that annoy me that they haven't been fixed. ... View more

Ow that is horrible! Make sure you check the actual locations on the two drives (origin and destination). It could be that the images are still there but are lost to the catalog somehow. ... View more

The max resolution of the web galleries is 2560 pixels on the long edge. That should be more than enough for any web use. How does the low resolution manifest itself for you? Indeed share a link so we can see.   when you export to avif or jxl, how does you 'upload to Adobe' ?  ... View more

That's really strange. This is exactly the method I used above and the images show up as hdr in safari, chrome and edge. You just have to click on the images to enlarge them to see the hdr. You won't see the hdr in the grid view. What versions of classic and cloudy are you using? Also what version of the OS? ... View more

Just realized I shared the private link above so replaced with the public link: https://lightroom.adobe.com/shares/cd71fe426d7a45c28ae667ebc2b14c6b Interestingly this actually does work in Safari and gives me HDR. @DdeGannes Yes just tried and the HDR in Lightroom Web galleries works fine in Edge. Firefox does not show the HDR, but Safari, Chrome, and Edge all do. ... View more